VOLO Operator Permissions
tip
Jump straight to the Examples section to see how to use the permissions for a few specific scenarios.
Operator Types​
There are 2 main types of operator within the VOLO system:
- Installer Operators
- Customer Operators
The difference between the two types is simply that Installer Operators can access VOLO systems belonging to multiple customers (all those where the Installer is responsible for the maintenance of the system), but a Customer Operator is restricted to one VOLO system, only.
This cannot be changed - a Customer Operator cannot be granted access to data within another Customer's account.
Apart from the difference mentioned above, Installer Operators and Customer Operators can be configured to have identical permissions if they wish to.
The system is designed to support a variety of different business relationships between Installers and End Users (Customers):
- Hands-off customers, who want only the bare minimum responsibility for maintaining their VOLO system
- Hands-on customers, who want to manage everything except the installation of the VOLO controllers
- Everything in between!
Many different scenarios can be supported, but we have included a few common configurations in the sections below.
Permission Overview​
The VOLO permissions are grouped by 'Resource'. Types of resource in VOLO include, Doors, Users, Sites, Events and various other items that are in some way managed through the VOLO Software.
Then, for each resource, you have the option of allocating different types of permission depending on what the operator
should be allowed to do within the system - for example, you may want someone to be able to View and Edit
existing Sites, but they shouldn't be able to delete them.
Resources and Permission types are described in full, below.
Types of Permission​
| Permission | Description |
|---|---|
| View | Allow operators to view the resource in question, but not create, make changes to or delete them |
| Create | Allow operators to create this type of resource |
| Edit | Allow operators to edit or make changes to this type of resource |
| Delete | Allow operators to delete this type of resource |
danger
Please be extremely careful when assigning Delete permissions.
Deleting a Customer, for example, would result in loss of all data belonging to that Customer (Controllers, Doors, Users, Events), so this permission should only be assigned to those Operators who fully understand the risks.
Types of Resource​
| Resource | Description |
|---|---|
| Installers | |
| Customers | |
| Sites | Sites found within a Customer's account. All Operators must have at least View persmissions. |
| Controllers | VOLO controllers - creating, editing or deleting should be restricted to Installer Operators |
| Doors | All operators should have at least View permissions for Doors. Create and Delete permissions should usually be restricted to Installers. |
| Events | View should be the only permission needed. |
| Operators | These permissions relate to the management of OTHER operators for the VOLO system. |
| Users | These permissions relate to users of the VOLO system - those who access the doors but NOT operators who log into the platform |
| Timezones | Many customers will require full access to Timezones if they actively manage the access schedules within their system |
| Holidays | |
| Access Levels | Many customers will require full access to Access Levels if they actively manage the access schedules within their system |
| Reports | View and Create permissions will be required for operators who wish to run reports through the system. |
| Licences | If the operator should have visibility of the VOLO licences, there should be no need for anyone to have more than View permissions. |
| CCTV | Only Installer operators should require these permission - these relate to configuring an integration with a CCTV platform |
| Cameras | Most operators should only require View permissions in order to review footage linked to events through the VOLO system |
Examples​
tip
You can combine the permission sets shown in the various examples below if you would like to create an Operator who is allowed to undertake a variety of different tasks within the system.
Minimum Permissions​
All operators must have at least the permissions shown in the table below. If you do not include these minimum permissions, it is likely that the operator will encounter errors when trying to navigate around the VOLO system.
info
The Y characters shown in the tables below indicate permissions that should be selected/granted when creating the operator.
| Resource | View | Create | Edit | Delete |
|---|---|---|---|---|
| Customers | Y | |||
| Sites | Y | |||
| Doors | Y | |||
| Events | Y | |||
| Operators | Y | |||
| Users | Y | |||
| Timezones | Y | |||
| Access Levels | Y |
Permission to Reset Fire Alarms​
Operators with the minimum permissions define above will be permitted to issue the Clear Fire Alarm command.
tip
Please review the instructions on how to reset fire alarms through VOLO.
Permission to Run Reports​
In order to run reports we have added the following to the minimum permissions identified above:
- Edit permission for Customers
- View permission for Reports
- Create permission for Reports
| Resource | View | Create | Edit | Delete |
|---|---|---|---|---|
| Customers | Y | Y | ||
| Sites | Y | |||
| Doors | Y | |||
| Events | Y | |||
| Operators | Y | |||
| Users | Y | |||
| Timezones | Y | |||
| Access Levels | Y | |||
| Reports | Y | Y |
Managing Users​
In order to fully manage users, we have granted the following additional permissions:
- Create permission for Users
- Edit permission for Users
- Delete permission for Users
| Resource | View | Create | Edit | Delete |
|---|---|---|---|---|
| Customers | Y | |||
| Sites | Y | |||
| Doors | Y | |||
| Events | Y | |||
| Operators | Y | |||
| Users | Y | Y | Y | Y |
| Timezones | Y | |||
| Access Levels | Y |
Remotely Unlock Doors​
In order to Unlock/Open Doors through the VOLO software, we have granted the following additional permissions:
- View permission for Controllers
- Edit permission for Doors
caution
The permissions required to remotely unlock doors will also make other features accessible, including:
- Controllers will now be visible to the Operator (but they cannot edit any settings)
- Operators will now be able to edit the configuration and settings related to Doors
| Resource | View | Create | Edit | Delete |
|---|---|---|---|---|
| Customers | Y | |||
| Sites | Y | |||
| Controllers | Y | |||
| Doors | Y | Y | ||
| Events | Y | |||
| Operators | Y | |||
| Users | Y | |||
| Timezones | Y | |||
| Access Levels | Y |
Managing Timezones & Access Levels​
In order to fully manage Timezones & Access Levels, we have granted the following additional permissions:
- Create permission for both Timezones & Access Levels
- Edit permission for both Timezones & Access Levels
- Delete permission for both Timezones & Access Levels
| Resource | View | Create | Edit | Delete |
|---|---|---|---|---|
| Customers | Y | |||
| Sites | Y | |||
| Doors | Y | |||
| Events | Y | |||
| Operators | Y | |||
| Users | Y | |||
| Timezones | Y | Y | Y | Y |
| Access Levels | Y | Y | Y | Y |